home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group96a.txt
/
000035_icon-group-sender _Fri Feb 2 10:20:25 1996.msg
< prev
next >
Wrap
Internet Message Format
|
1996-09-05
|
1KB
Received: by cheltenham.cs.arizona.edu; Fri, 2 Feb 1996 12:42:47 MST
Date: Fri, 2 Feb 1996 10:20:25 -0600
From: jeffery@dragon.cs.utsa.edu (Clinton Jeffery)
Message-Id: <9602021620.AA10426@dragon.cs.utsa.edu>
To: jk@soas.ac.uk
Cc: icon-group@cs.arizona.edu
In-Reply-To: <25A6207A9E@soas.ac.uk> (message from Jonathan Kaye on Fri, 2 Feb 1996 10:46:15 GMT)
Subject: Re: nticont for NT (9.1)
Content-Length: 832
Errors-To: icon-group-errors@cs.arizona.edu
Status: O
[Jonathan Kaye writes, asking how to build the Icon Program Library
using the Windows Icon 9.1 release:]
JK> Can you PLEASE tell us (icon-group) where to find the nticont.exe
JK> binary for 9.1. I need it to update all my procs & gprocs to 9.1
JK> without having to do them one by one.
wicont.exe accepts *.icn wildcards that help in translating large numbers
of files. The window that it opens normally waits for a user keystroke on
termination, so that you can read the messages; a -q option disables this
for use in scripts.
If there are numerous folks who need NT console binaries, I'll produce a set.
Since they don't run under Win3.1 and probably don't run on Warp or Windows95,
I'm not sure what the level of demand for them is.
Clint Jeffery
jeffery@ringer.cs.utsa.edu
The University of Texas at San Antonio